Tech Arsenal 1

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 1 / Tech Arsenal (Arsenal Computer).ISO / tek-06 / nwl11e.zip / README.TXT < prev next >

Wrap

Text File | 1992-07-06 | 54KB | 1,134 lines

NetWare Lite v1.1 (7/02/92) Print this file and save it for future reference. To print this file to a local printer, 1. Insert the DRIVER diskette into drive A:. 2. At the DOS prompt, type "A:" and press <Enter>. 3. At the DOS prompt, type "COPY README.TXT PRN" and press <Enter>. CONTENTS 1. New Features 2. Installing NetWare Lite and Logging In 3. Upgrading NetWare Lite v1.0 to NetWare Lite v.1.1 4. General Information 5. Optimize Your Network Server 6. Printing 7. Network Directory and File Sharing 8. Basic Network Application Configuring Tips 9. Basic Troubleshooting 10. NetWare Lite and NetWare Compatibility 11. Auxiliary NetWare Files 12. NetWare Lite and Windows 1. NEW FEATURES * NetWare Lite Cache software makes the network run 3 to 6 times faster by reducing time waiting for the hard disk. For more information, after installing a NetWare Lite server, print the CACHE.TXT file in the NWLITE directory. * NET SAVE retains mapped drives, captured ports, and DOS environment variables. At the DOS prompt, type "NET SAVE" and press <Enter>. The mapped drives, captured ports, and DOS environment variables are saved in a file named NLLOGIN.BAT. Next time you want to log in, you can type "NLLOGIN" (instead of "NET LOGIN") and press <Enter> to log in, automatically map the drives, capture the ports, and set up the DOS environment to the settings in the NLLOGIN.BAT file. * SERVER.EXE and CLIENT.EXE can be loaded into upper memory (between 640 KB and 1024 KB). You must have an upper memory block (UMB) with at least 64 KB available to load SERVER.EXE into upper memory. Modify the SERVER and CLIENT lines in STARTNET.BAT to include the specific load high command for your memory manager. Example: If you use DR DOS 6.0, change the SERVER line to HILOAD SERVER and the CLIENT line to HILOAD CLIENT. Although SERVER.EXE needs an upper memory block of at least 64 KB to load, it may not use the entire 64 KB. Once SERVER.EXE is loaded, the remaining upper memory can be loaded with other programs like CLIENT.EXE. If SERVER.EXE is configured so it requires more than 64 KB and it will not fit in an upper memory block, you receive a message and SERVER.EXE does not load. * NetWare Lite v1.1 SERVER.EXE's default size is about 10 KB smaller than in NetWare Lite 1.0 SERVER.EXE's default size. If you have a two- computer network and set the server configuration to the minimum values, SERVER.EXE would be approximately 33 KB. The size of SERVER.EXE is relative to the server configuration settings. * You can unload SERVER.EXE and CLIENT.EXE from memory. This makes more memory available for applications when you are not using the NetWare Lite network. NOTE: You can only unload programs in reverse loading order. CLIENT.EXE must be unloaded before SERVER.EXE on a server/client station. To unload CLIENT.EXE from memory, at the DOS prompt, type "CLIENT U" and press <Enter>. To unload SERVER.EXE from memory, at the DOS prompt, type "SERVER U" and press <Enter>. * Commands are more like native NetWare. Added a NET WHOAMI alias for NET INFO and a NET USERLIST alias for NET ULIST. * You can use the NET SLIST command to get a list of the servers on the network without logging in. At the DOS prompt, type "NET SLIST" and press <Enter>. * NET AUDIT and NET RECEIVE display their status (on or off). At the DOS prompt, type "NET RECEIVE" or "NET AUDIT" and press <Enter>. The status (on or off) appears. * You can use NET RECEIVE to set a message-display time limit at your workstation. At the DOS prompt, type "NET RECEIVE number" and press <Enter>. Replace number with the number of seconds (0 to 1500) you want the message to remain on the screen. If you enter 0, the message remains on the screen until you simultaneously press <Ctrl> <Enter>. * You can have client workstations notified when print jobs are complete. Set the NET CAPTURE notify option to yes. (The notify option default is set at no.) Example: NET CAPTURE LPT1 N=Y Your client workstation is notified when your print job is completed. To clear the notification, simultaneously press <Ctrl> <Enter>. * CD-ROM drive support. You can install CD-ROM drivers on a server-only computer or on a server-client computer. Additional information is available on Novell's automated fax system. 2. INSTALLING NETWARE LITE AND LOGGING IN NOTE: If you have NetWare Lite v1.0 software on the computer, use the upgrade option so your network configuration remains intact. Determine Hardware Interrupt and Port Address Requirements If your computer has an internal or external modem, bus mouse, fax board, scanner, or other add-on board, determine if any of the device interrupt levels (IRQ) or port addresses (I/O addresses) will conflict with the NetWare Lite default interrupt 3 and port address 300 (most network cards are set to these values at the factory). If there is a conflict on the actual card, change the NetWare Lite interrupt level or port address values so they don't conflict with the other devices. Then select the corresponding interrupt and port address setting during installation. For most computers, you can change the interrupt level and port address during Step 3 of the NetWare Lite installation. For IBM PS/2 computers, change the interrupt level and I/O, EPROM (port address) on the PS/2 reference diskette. Use an interrupt (IRQ) for your network card. The following table shows what the IRQ levels are used for in XT and AT computers. _______________________________________ |IRQ | XT | AT (286, 386, 486) | |____|_____________|____________________| | 0 | | timer output 0 | | 1 | | keyboard | | 2 | EGA/VGA | EGA/VGA | | 3 | COM2 | COM2 | | 4 | COM1 | COM1 | | 5 | hard disk | LPT2 | | 6 | | floppy disk | | 7 | LPT1 | LPT1 | | 8 |Not Available| real time clock | | 9 |Not Available| | | 10 |Not Available| | | 11 |Not Available| | | 12 |Not Available| | | 13 |Not Available| co-processor | | 14 |Not Available| hard disk | | 15 |Not Available| | |____|_____________|____________________| The network card needs to use a unique I/O address. The following table shows possible address conflicts. ____________________________________________________ | I/O ADDRESS | POTENTIAL CONFLICT DEVICES | |_____________|______________________________________| | 1F0 | AT disk controller | | 200 | game controller/joystick (200-20F) | | 220 | Novell network keycard | | 240 | | | 260 | LPT2: (278-27F) | | 280 | LCD display on Wyse 2108 PC | | 2A0 | | | 2C0 | | | 2E0 | COM4:, GPIB-Adapter 0 (2E1) | | | COM2:, Data acquisition (300-31F) | | 300 | | | 320 | XT hard disk interface (320-32F) | | 340 | | | 360 | LPT1:(378-37F) | | 380 | SLDC/Sec Bi-Sync interface (380-38C) | | 3A0 | Primary Bi-Sync interface (3A0-3A9) | | | Monochrome display (3B0-3BB) | | 3C0 | EGA display control (3C0-3CF) | | | CGA display control (3D0-3DF) | | 3E0 | COM3: (3E8-3EF) | | | floppy disk controller (3F0-3F7) | | | COM1: (3F8-3FF) | |_____________|______________________________________| Install NetWare Lite Software Insert the PROGRAM diskette into drive A:. At the DOS prompt, type "A:" and press <Enter>. At the DOS prompt, type "INSTALL" and press <Enter>. Follow the instructions and help provided on the screen during installation. If your computer has an internal or external modem, bus mouse, fax board, scanner, or other add-on board, at Step 3 change the interrupt level (IRQ) and port address (I/O address) so that they do not conflict with other device interrupt levels or port addresses. (You should have changed the network board's interrupt level and port address before installing the NetWare Lite software.) NOTE: Your original AUTOEXEC.BAT and CONFIG.SYS files are saved in the directory with a .BNL (Before NetWare Lite) extension. Your NET.CFG file is saved in the NWLITE directory as NET.BNL. Make sure that your AUTOEXEC.BAT path statement includes the DOS directory. If it does not, the DOS SHARE program will not load. Start NetWare Lite Remove the disk from drive A: Restart your computer by simultaneously pressing <Ctrl>, <Alt>, and <Del>. As the computer is booting, the STARTNET.BAT file loads SHARE, LSL, the LAN ODI driver, IPXODI, SERVER, and CLIENT. If IPXODI reports an error (such as a conflict in the interrupt setting or port address) when loading, check the interrupt settings and I/O address (or port address) setting on other boards in the computer to determine if they conflict with the network board's interrupt settings. Also check NET.CFG to make sure the settings match the network board. Make sure you set the network board setting correctly when installing NetWare Lite. If interrupt settings conflict, change the interrupt setting on the network board and install NetWare Lite again or edit NET.CFG and reboot. At the DOS prompt, type "NET" and press <Enter>. You will be prompted for a username. Verifying Network Connections Insert the PROGRAM diskette into drive A:. At the DOS prompt, type "A:" and press <Enter>. At the DOS prompt, type "INSTALL" and press <Enter>. Highlight "Verify network connections" and press <Enter>. Make sure that the workstation name appears in the list. Verify the network connections for all workstations on the network. All the workstations on the network should appear on the list. Let each computer run for at least 2 minutes to make sure there are no intermittent problems. If a computer doesn't appear in the list, there is a hardware problem (cards, cables, etc.) or the network card is configured incorrectly. Exit the installation program on each workstation. Logging in After Installing NetWare Lite After installing the first server on a new NetWare Lite network, log in as SUPERVISOR (the only user defined on the network). Type "NET LOGIN SUPERVISOR" and press <Enter>. NOTE: The SUPERVISOR account on a newly installed network does not have a password. For network security, set a password on the SUPERVISOR account soon after the network is installed. DO NOT FORGET THE SUPERVISOR PASSWORD. When additional servers are installed on an existing NetWare Lite network, defined users, network directories, and network printers are automatically available. You should log in using one of the defined user accounts. Reinstall NetWare Lite Software If you have to reinstall NetWare Lite, you can save the database of network directories, network printers, server configuration, and printer control and the database of network users by backing up the network management system files before reinstalling NetWare Lite. After reinstalling NetWare Lite, you can restore the system files so the users, network printers, network servers, server configuration and printer control are the same as they were when the last system file backup was made. For more information about backing up and restoring system files, see page 28 in the manual. 3. UPGRADING NETWARE LITE v1.0 to NETWARE LITE v1.1 When you upgrade from v1.0 to v1.1, the server and network information remain on the network. The users, network directories, and network printers don't have to be set up again. The upgrade option can be used on all computers that have NetWare Lite v1.0 installed. Insert the PROGRAM diskette into drive A:. At the DOS prompt, type "A:" and press <Enter>. At the DOS prompt, type "INSTALL" and press <Enter>. When the NetWare Lite Install Menu appears, highlight "Upgrade this machine to v1.1" and press <Enter>. The NetWare Lite v1.1 software is loaded. When upgrading floppy-only NetWare Lite software, the INSTALL program asks for a path. Type "A:" and press <Enter>. Reboot your computer so NetWare Lite 1.1 is loaded. 4. GENERAL INFORMATION Files on NetWare Lite diskettes that end with an "@" are compacted and will not work until they are unpacked. The INSTALL program unpacks compacted files and renames them removing the "@". * Questions and Answers a. How can I tell if my hardware and drivers are functioning properly? After loading STARTNET.BAT, verify the network connections as explained in the manual on page 7. Let each computer run for at least 2 minutes to make sure there are no intermittent problems. If a computer doesn't appear in the list, there is a hardware problem (cards, cables, etc.) or the network card is configured incorrectly. b. I can't find an ODI driver for my card. Can I use IPX.COM? Yes. In the STARTNET.BAT file, replace the following statements with IPX.COM: lsl NE2000 (Or applicable driver.) ipxodi a (The above three statements are equivalent to the older IPX.COM.) c. What causes network drivers, certain DOS commands, and some programs to lock up and act unpredictably (i.e. DOS extend error 59, WordPerfect disk error 51)? This is probably a hardware conflict or a memory conflict with the memory area between 640 KB and 1024 KB. Some network cards use a shared memory address that resides in system memory (upper memory). Often the memory address used by the card is written over by another program which can cause unpredictable results. You need a memory management program with the capability of excluding specific areas of memory from other programs. See the memory manager's documentation to see how to exclude the memory and refer to the network card's documentation to see how much memory to exclude. Other possible causes include a bad cable, a cable that is non- standard, a homemade cable, a wrong terminator (use 50 ohm for Ethernet and 93 ohm for ARCnet), no ground terminator, or noise on the wire. If using 10Base-T, connect the 10Base-T cable to a concentrator, not directly to the second computer. d. What are the possible conflicts that could interfere with default settings on network cards (IRQ 3 and I/O address 300)? The most common IRQ3 conflicts occur when COM2 is used (as a second serial port or for an internal modem, or fax board). These conflicts may not show up until you try to use COM2:, or in the case of a bus mouse, until you try to use the NET command with the bus mouse initialized. Use fax document #212 or the chart previously given in this document. e. I receive errors in DOS applications such as share violations, unable to access file XXXX errors, errors entering and exiting an application, or the station hanging. What can I do? Change the application directories' default rights to READ. Some applications require Write access to the directory. If this is the case, change the .EXE, .OVL and .COM files rights to READ ONLY using the DOS command ATTRIB or third party software. Remove the TSRs running on your computer one at a time and run the application again to determine if a TSR is causing the problem. (Load NetWare Lite using the STARTNET command before you load other TSRs.) Check for conflicts on interrupts used by the hardware. Increase the value of "FILES=XX" in CONFIG.SYS. Example: "FILES=50." Increase the value of the "Client tasks" in the Net Utility Server Configuration. Make sure there are at least 10 tasks per client connected to the server for DOS and at least 15 tasks per client connected to the server for Windows. Check the application's setup or the configuration section that applies to network selection. Select NO NETWORK or OTHER. Do not select NETWARE or NOVELL. Check the server status. Make sure that the PEAK values are not as high as the configured (CFG) values. If the PEAK values are approaching the configured values, increase the applicable configured values and reboot the computer. Make sure the application directory is included in the PATH statement in AUTOEXEC.BAT or STARTNET.BAT. Check the memory requirements of the program and PC memory for possible problems. Increase the SHARE file and lock parameters in STARTNET.BAT or AUTOEXEC.BAT. Example: SHARE /F:8000 /L:200 [The file (/f) parameter is not applicable in DR DOS 6.0.] * Load NETBIOS if an application requires it. * Load SPX if an application requires it. Modify the STARTNET.BAT file "IPXODI A" command to "IPXODI D." When the "A" is removed, both IPXODI and SPX is loaded. You can type "IPXODI ?" at the DOS prompt to see a list of all available options for IPXODI. * Avoid mapping local drives as network drives. You can map local drives (for example, A: or B:) and use them temporarily as network drives; however, we Do Not recommend doing this. If you run out of drive letters to map, increase LASTDRIVE in your CONFIG.SYS file. * Do Not use ASSIGN with NetWare Lite. The DOS (3.3) reference manual recommends the use of SUBST instead of ASSIGN. * WARNING: Caches, other than the NetWare Lite Cache, may need to have delayed writes, deferred writes, posted writes, or queued writes disabled if they are used with NetWare Lite. Many cache programs "wake up" to do writes in the background, they do not protect themselves from re-entry with a DOS-critical section callout. If you use a cache (other than the NetWare Lite Cache) with deferred writes, posted writes, or queued writes turned on, you may get random hangs, data corruption, or other abnormal behavior. To use a cache other then the NetWare Lite Cache, call the cache company's technical support group to find out if their cache's deferred writes, posted writes, or queued writes work with NetWare Lite. Many caches don't allow delayed writes, deferred writes, posted writes, or queued writes when using a peer-to-peer network. However, the NetWare Lite Cache can use delayed writes. If you are using a cache that has one of the above options, make sure the option is turned off. * Do not make server names 15 characters long if you remotely manage servers. If you remotely manage a server with a name that is 15 characters long, the server will hang. To fix the problem, make the server name less than 15 characters long. 5. OPTIMIZING YOUR NETWORK SERVER * Modify the number of receive buffers and number of I/O buffers. Depending upon the number and frequency of requests to the server, increasing the number of receive buffers and I/O buffers may enhance server performance. The number of receive buffers doesn't need to be more than 2 above the number of simultaneous connections, but it shouldn't exceed 12. Generally 8 to 12 receive buffers and 1 to 4 I/O buffers are sufficient for up to 25 connections. * Modify the receive buffer size and I/O buffer size for the network. Using multiples of 512 bytes, increase the receive buffer size up to the maximum supported by the network topology (for example, Ethernet or Token ring) or a maximum of 8192 bytes. However, increasing the size of the receive buffer increases the size of the server software when it is in RAM. If you enter too large a number at the receive buffer size field in the Server Configuration option, NetWare Lite truncates the value to the highest value that the network card can transmit or receive. Increasing the receive buffer size lets clients request more data from or send more data to the server with each read and write operation. When more data is sent, fewer requests to the disk are necessary so you get better performance from the server. * Unfragment files or optimize disk. MAKE SURE THAT SERVER.EXE IS NOT RUNNING WHEN YOU UNFRAGMENT FILES! Fragmented files adversely affect server performance. Periodically unfragment files on each server's hard disk using a disk optimizing or a disk compression tool. Never run any low-level disk repair utilities (including CHKDSK /F or disk optimizing utilities) on the hard disk while the server (SERVER.EXE) is loaded. Doing so can corrupt data stored on the hard disk. Do not run low-level utilities from a client that has a drive mapped to the server. * Use SUBST instead of MAP for network drives on a local server. If your computer has network directories on its hard drive, you can use the SUBST command instead of NET MAP command. It is more efficient to use SUBST to access network directories on your hard disk than it is to use NET MAP. 6. PRINTING * Questions and Answers a. Why does a status message "Printer off Line" or "Printer Out of Paper" pop up when I try to print even though neither of these situations is accurate? Check the network printer configuration to make sure it is configured for the port (LPT1, LPT2, LPT3) that it is actually connected to. Example: If the printer is connected to LPT1 on the server, the network printer configuration must be set to LPT1. If the network printer configuration and printer port are correct, increase the printer configuration "Error wait time" by 15-second increments and try again. b. One of the servers has intermittent problems when trying to print. Sometimes the server hangs and other times the print job disappears without being printed. If you are using LPT1 on the server, make sure that your network card is NOT set to I/O 360. This port address overlaps with the I/O address for LPT1 (378). If LPT2 is used, INT 5 will cause a conflict. c. How can I let NetWare Lite know that I have changed the IRQ and I/O address on my network LAN driver without reinstalling the program? Edit C:\NWLITE\NET.CFG. If the file is not there, create one like this: #Setup the NE2000 card (This is a comment line) link driver NE2000 (Enter the ODI driver name here in place of NE2000.) int 3 port 300 MEM D000 (This line is used only when a card has a shared memory address.) Enter the correct settings into this file and reboot the computer. The driver loads with the correct settings. If you change network cards, change the NET.CFG file to match the settings on the new card and change the STARTNET.BAT driver name to the new driver name. MicroChannel computers typically do not require NET.CFG. * Using characters per second and print buffers. The print buffer is an area in memory where characters are stored before being printed. The larger the print buffer size, the fewer times the server must to go to disk to read characters to print. If the "Characters per sec" value is high (relatively speaking), the printer is driven faster and the DOS running on the computer is interrupted more often to send characters to the printer. The opposite is also true if the value of the "Characters per sec" is low (relatively speaking) and the print buffer size is small. Tune these values to the speed or chosen speed of the printer. If the printer is physically a "slow" printer (like a serial printer), setting the "Characters per sec" parameter to a high number does not affect the speed of printing, but it can adversely affect the foreground DOS process. For serial printers, the "Chars per sec" value should be about the same as the printer baud rate divided by 10. Example: If the baud rate is 9600, the "Char per sec" value should be about 960. * Access local network printers only through the network. When you have a network printer attached to your workstation, capture a port when you need to print to the attached printer. If you print directly to the printer without capturing the port, you may corrupt print jobs or get a write error. * Make network printers location-independent. Example: Your server, named DEPT_SERVER is an 8 Mhz 286 computer with a 40 MB hard disk. It has a network printer named LASERJET. Clients capture ports to LASERJET and print to it almost every day. You buy a 50 Mhz 486 computer with a 1 GB hard disk and want to move the LASERJET network printer to the new computer. You set up the new computer and install the NetWare Lite software, calling the server HOT_SERVER. You then create a new network printer named LASERJET (same name as before) on HOT_SERVER. Remove the network printer from DEPT_SERVER. When clients capture the LASERJET network printer (without specifying the server name in the command line), the LASERJET network printer is on HOT_SERVER, not DEPT_SERVER. Nothing in the client's STARTNET.BAT or AUTOEXEC.BAT needs to be changed. In fact, the client does not need to know that the computer that the LASERJET network printer was connected to has changed. * Give each network printer a name that describes the printer. A good network printer name for a LaserJet II printer would be LASERJET_II or LJ2. Other descriptive network printer names could be EPSON_DOT or OKIDATA_DOT. Network printer names like PRINTER1 or PRINTER2 do not describe the printer and do not help users on the network determine which printer to use. * When sending print jobs to postscript printers or when you want to print in Novell byte stream mode, make sure that your NET CAPTURE command includes the following settings: Banner equals No (B=N) Tabs equals Zero (T=0) Formfeed equals No (F=N) Setup string equals Default (S=DEFAULT) NOTE: The Default setup string should not have any values when it is used for postscript printing or when it is used for byte stream mode. If your print job gets split to multiple jobs when printing or if the first part of a printed document is in fonts and the rest of the document isn't, increase the WAIT value (W=10) to a value higher than 10 seconds, for example, 20 seconds (W=20). * You can define up to 64 setup strings for each network printer. Each setup string can have up to 64 two-digit hexadecimal characters. A setup string is a series of characters that put the printer into a particular mode (for example, landscape mode or large character mode). By default, the DEFAULT setup string is set to nothing. Make the DEFAULT setup string a sequence of values that resets the printer. Many printers use the string "1B 45" (<Esc>E) to reset the printer. Check your printer documentation to determine which setup string sequence value resets the printer and which sequences place the printer into other modes. Setup strings are always entered using hexadecimal codes. You can submit jobs that print in different printer modes by defining multiple setup strings for a network printer. Use setup strings as part of the NET CAPTURE command or in the NET menu utility "Print" option. 7. NETWORK DIRECTORY AND FILE SHARING * Give each network directory a name that describes the contents of the network directory to help locate applications and files. A good name for a network directory that contains the WordPerfect application would be WORDPERFECT or WP. Other descriptive network directory names could be GAMES, PUBLIC, or TURBOC. Network directory names like CDRIVE or DDRIVE do not describe the directory contents so they do not help network users find applications or files. NOTE: During NetWare Lite installation, the network directory CDRIVE is created for you. When you are familiar with network directories, remove CDRIVE and replace it with one or more descriptive network directories. * Make executable files (*.EXE, *.COM, *.BAT, *.OVL) READ-ONLY files, or place executable files in a network directory with READ default access rights. If an executable file is not marked READ ONLY or is not in a network directory with the default access right READ and the file is accessed by more than one user, the users may be temporarily denied access to a file. To make executable files READ-ONLY, see the DOS documentation for the ATTRIB command. To make the network directory default access rights READ, see "Create or Modify Network Directories" in the NetWare Lite manual. * Make network directories location-independent. Example: Your server, named DEPT_SERVER, is an 8 Mhz 286 computer with a 40 MB hard disk. It has a network directory named ALL_APPS. All clients map drives to ALL_APPS and use it every day. You buy a 50 Mhz 486 computer with a 1 GB hard disk, and want to move the ALL_APPS network directory to the new computer. You set up the new computer and install the NetWare Lite software, calling the server HOT_SERVER. You then create a new network directory named ALL_APPS (same name as before) on HOT_SERVER. Copy the files from DEPT_SERVER to HOT_SERVER. Remove the network directory ALL_APPS from DEPT_SERVER. Now when clients access the ALL_APPS network directory (without specifying the server name in the command line), the ALL_APPS network directory is on HOT_SERVER, not DEPT_SERVER. Nothing in the client's STARTNET.BAT or AUTOEXEC.BAT needs to be changed. In fact, the client does not need to know that the computer that the ALL_APPS network directory was on has changed. * Include the PATH Command in AUTOEXEC.BAT or STARTNET.BAT to search for applications. Include network directories that contain applications (executable files) that are mapped to drive letters in the DOS environment variable path. Example: If the AUTOEXEC.BAT or STARTNET.BAT file contains NET MAP L: DR_DOS_6 and NET MAP M: NWLITE, include L: and M: in the path. Use the statement "PATH=%PATH%;L:\;M:\;" in the AUTOEXEC.BAT. NOTE: Each drive (letter, colon, and backslash separated by a semicolon) included in the PATH command is searched when an executable filename is entered and executed at the DOS prompt. If an application or executable file is located in any of the drive letters included in the PATH command, the application or executable file is launched. When NetWare Lite is installed, the INSTALL program searches for an AUTOEXEC.BAT file. If a PATH command is included in the file, the installation program adds "C:\NWLITE" to the path command. If there is no PATH command, the installation program adds the command "PATH=C:\NWLITE" to the AUTOEXEC.BAT file. 8. BASIC NETWORK APPLICATION CONFIGURING TIPS Installing applications on NetWare Lite may be different than installing the same applications on regular NetWare because NetWare Lite is a peer-to-peer network. If an application requires configuration information when it is installed, determine which workstations will use the application. Example: The application TESTAPP.EXE is being installed and the installation program asks what kind of monitor will be used with the application. The computer you are at has a VGA screen, but no other computer on the network has a VGA screen. If you select VGA, when the application is run from across the network on a computer that has a CGA screen, the application may not properly function. If the installation procedure asks what type of network you are using, don't select NOVELL or NETWARE. Select OTHER, IBM COMPATIBLE, DOS, NETBIOS, or PEER-TO-PEER. For more details, see Appendix B in the manual. Make all executable files READ-ONLY using the DOS ATTRIB command. Check the PATH statements and configuration files for incorrect paths to programs and data files. Make sure SHARE is loaded with sufficient locks and memory (/L and /F parameters). See the DOS documentation. Check the CONFIG.SYS for sufficient FILES and BUFFERS on all nodes. Also find out if the application has a separate method of configuring the number of open files. Clipper compiled applications often have a separate configuration method. Separate shared and non-shared files into different mapped directories. Make sure you have sufficient connections and tasks on the server to do the job. 9. BASIC TROUBLESHOOTING Use Novell IMSP certified drivers and boards. Establish the sequence of operations that cause the problem. Is it a random problem? Does it only happen in a particular application or particular combination of applications? What do the applications do? This background information will help you decide if the problem is hardware or software. Get the layout of the network. Find out how many server-clients, server-only, and client-only computers are on the network. Find out what type of network card and interrupt and port address settings are installed in each computer. Find out what drivers, printer models, brand and type of computers, versions of DOS, and additional cards and other peripherals are on the network. Resolve all hardware problems first. Some symptoms that appear to be application related are caused by connectivity issues. Reboot the computer without loading the network software. See if the problem exists when the network software is not loaded. Find out if the applications are network versions. Many non-network applications will work on the network, but some will not. 10. NETWARE LITE AND NETWARE COMPATIBILITY The shell's 25th line message may block a NetWare Lite server, causing stations that are attached to the server to appear to hang. NetWare Lite functions on a single LAN segment so NetWare Lite packets DO NOT cross Novell routers (NetWare Lite packets do cross MAC layer bridges or repeaters). At sites that have an existing NetWare network, each NetWare Lite network is limited to a single LAN segment of the network. If a workstation will use both NetWare Lite and native NetWare (which requires NETx.COM), load the software in the following order: __________________________________________________ | SOFTWARE LOADING ORDER | |__________________________________________________| | SOFTWARE | SERVER | CLIENT | BOTH | |_______________________|________|________|________| | SHARE.EXE | Load | | Load | |_______________________|________|________|________| | If using IPXODI load | | | | | LSL | | | | | Network board driver| Load | Load | Load | | IPXODI | | | | |_______________________|________|________|________| | If using IPX load the | | | | | generated IPX file | Load | Load | Load | |_______________________|________|________|________| | SERVER.EXE | Load | | Load | |_______________________|________|________|________| | CLIENT.EXE | | Load | Load | |_______________________|________|________|________| | Log in to the NetWare Lite Network and capture | | ports and map drives before loading NETx.COM | |__________________________________________________| | NETx.COM | Load | Load | Load | |_______________________|________|________|________| NOTE: The NetWare Lite Cache can be loaded as a device driver from CONFIG.SYS or it can be loaded anytime as a TSR. After installing CLIENT.EXE in a workstation that also uses the NetWare shell, modify your AUTOEXEC.BAT or appropriate batch file to load the files in the correct order. NOTE: The NetWare Shell maps the SYS:LOGIN drive to the drive after the NetWare Lite LASTDRIVE specified in CONFIG.SYS. If LASTDRIVE is not set, DOS defaults to drive E:, so drive F: is mapped to SYS:LOGIN. We recommend using the "MAP *1:=" command in your login script to map the drive after the specified NetWare Lite LASTDRIVE. If you use the relative drive mapping (above) instead of the absolute drive mapping, you wont have to change drive mappings as often if you change your last drive. However, if certain drives must be mapped to specific letters, changing LASTDRIVE may change which drive letters are mapped. All drive letters (A: through Z:) can be mapped to NetWare servers (NetWare Lite can only map A: through LASTDRIVE). 11. AUXILIARY NETWARE FILES The following programs are included with NetWare, but are not documented in the NetWare Lite manual. These programs are not necessary for NetWare Lite to run, but they add functionality for some situations, and provide some fun too. DEDICATE.COM This small program can be run on a dedicated NetWare Lite server or on NetWare Lite client/servers when the keyboard will not be used for a while. DEDICATE.COM improves server performance by polling the keyboard, keeping SERVER.EXE out of DOS, and letting SERVER.EXE use more cycles per operation. To run DEDICATE.EXE, while SERVER.EXE is running, type DEDICATE and press <Enter>. DEDICATE.COM remains active until you press a key on the keyboard. UPATCH.EXE This is the Universal Patch Program. It applies patches to target files. For information on NetWare Lite patches, customers in the U.S. and Canada can call Novell's 24-hour automated fax service at (800) 638-9273. Press the asterisk (*) key at the beginning of the recorded message. IPXSYNC.EXE This program can be used to synchronize activity on a Novell network. The usage is IPXSYNC string [count] (default count: 1). Include IPXSYNC and a string in any batch files when it is important that a specific computer is running before the batch file continues execution. IPXSYNC broadcasts the string until another computer broadcasts the same string. Then both stations continue running. Example: If you have three computers on your network and each computer has a network drive you want to map to, include the string "IPXSYNC READY 2" in all three computers' STARTNET.BAT files after the SERVER statement and CLIENT statement and before the drive mappings and port capture statements. When STARTNET.BAT gets to the "IPXSYNC READY 2" line, it will not continue the execution until two other computers on the network are issuing the "READY" message. NETBIOS.EXE Some applications require NETBIOS.EXE. If an application requires NETBIOS, load it at the DOS prompt after loading IPXODI and before loading the application. For more information on NETBIOS.EXE, contact the nearest Novell Authorized Reseller. NLSNIPES.EXE This is a game for one to five players. Everyone who wants to play NLSNIPES must map a drive to the same network directory. * For instructions on how to move and shoot, type "NLSNIPES /H" and press <Enter>. * To run NLSNIPES.EXE, type NLSNIPES. When asked for your initials, type two initials to identify your sniper. The first person to run NLSNIPES is the starter. As others run NLSNIPES and enter their initials, a sniper appears for the game. When the group is ready to play, the starter presses <Enter> to begin the game. Move your sniper through the maze killing snipes generators, and other snipers. If a "Sharing Violation error..." occurs, press F (Fail) to clear it and continue. This error can be avoided by typing "NET MAP ..." and using the mapped drive to a local disk instead of using the local disk directly. TASKID.COM This program is used when running Windows 3.0 in real or standard mode. Copy this program from the NWLITE directory to the WINDOWS\SYSTEM directory. TBMI.COM This program is used when running Windows 3.0 in real or standard mode. Copy this program from the NWLITE directory to the WINDOWS\SYSTEM directory. Include the command "TBMI" in the STARTNET.BAT file immediately after the "IPXODI" command. TBMI2.COM This program is used when running Windows 3.1 in standard mode. Copy this program from the NWLITE directory to the WINDOWS\SYSTEM directory. Include the command "TBMI2" in the STARTNET.BAT file immediately after the "IPXODI" command. VIPX.386 This program is used when running Windows 3.0 and 3.1 in enhanced mode. Copy this program from the NWLITE directory to the WINDOWS\SYSTEM directory. 14. NetWare Lite and Windows Before Installing Netware Lite and Windows 1. Decide what cache you want to use. NetWare Lite comes with the NetWare Lite Cache and it is designed to work with NetWare Lite. If you want to use SMARTDRV or another cache, you MUST turn off the write cache. WARNING: SMARTDRV's and other caches' write cache must be turned off because when they "wake up" to do writes in the background, they do not protect themselves from re-entry with a DOS-critical section callout. If you use any cache (other than the NetWare Lite Cache) with deferred writes, posted writes, or queued writes turned on, you may get random hangs, data corruption, or other abnormal behavior. WARNING: Do not use SMARTDRV and NetWare Lite Cache at the same time. 2. If you are going to use the NetWare Lite Cache, edit the AUTOEXEC.BAT file to remove the SMARTDRV command or the other cache's command. 3. If you are going to use SMARTDRV or another cache, do the following: See the cache's documentation to find out how to turn off the write cache. Do not install the NetWare Lite Cache when installing NetWare Lite. Installing/Modifying NetWare Lite and Windows 1. Install NetWare Lite. 2. From the DOS prompt (before you start Windows), copy the files TASKID.COM, TBMI.COM, TBMI2.COM and VIPX.386 from the NWLITE directory to the WINDOWS\SYSTEM directory on your hard disk. 3. Edit the SYSTEM.INI file in the WINDOWS directory. Under the [386enh] heading: UniqueDOSPSP=true PSPIncrement=5 OverLappedIO=off TimerCriticalSection=10000 ReflectDOSInt2A=true Modify the "network=*vnetbios, *dosnet" line to include "VIPX.386." Example: network=*vnetbios, *dosnet, VIPX.386 4. Make sure the Windows Setup System Information has the Network field set to "NO NETWORK INSTALLED." Do not select "NOVELL NETWARE ..." unless you are also connected to a native Novell NetWare network (like NetWare v2.2 or NetWare v3.11). While in the WINDOWS directory, type SETUP and press <Enter>. The Windows Setup screen appears. Highlight "Network" and press <Enter>. Highlight "NO NETWORK INSTALLED" and press <Enter>. The Windows Setup screen appears and the "Complete Changes" field is highlighted. Press <Enter> to make the change. Press <F3> to exit SETUP. 5. If you are going to use Windows in the REAL or STANDARD mode, execute the appropriate file (TBMI.COM or TBMI2.COM). The following matrix shows networking programs needed for specific DOS and Windows environments. It also specifies if and when to load the program. _________________________________________________________________________ | | WINDOWS 3.0 || WINDOWS 3.1 | |______|________________________________________||________________________| | DOS | REAL | STANDARD | ENHANCED || STANDARD | ENHANCED | |______|_____________|_____________|____________||__________ |____________| |MS DOS|TBMI.COM * |TBMI.COM * |VIPX.386 ***||TBMI2.COM *|VIPX.386 ***| | 3.x |TASKID.COM **|TASKID.COM **| || | | | 4.x | | | || | | | 5.x | | | || | | |_____ |_____________|_____________|____________||___________|____________| |DR DOS|TBMI.COM * |TBMI.COM * |VIPX.386 ***||TBMI2.COM *|VIPX.386 ***| | 6.x |TASKID.COM **|TASKID.COM **| || | | |______|_____________|_____________|____________||___________|____________| | | | * = Include the command "TBMI" or "TBMI2" in the STARTNET.BAT file | | immediately after the "IPXODI" command. | | | | ** = Load immediately after entering a Windows DOS box by typing | | "TASKID" at the DOS prompt and unload before exiting a Windows | | DOS box by typing "TASKID U" at the DOS prompt. | | | | *** = Make sure VIPX.386 is in the WINDOWS/SYSTEM directory and the | | SYSTEM.INI file "network=*vnetbios, *dosnet" line includes | | "VIPX.386". | |_________________________________________________________________________| Before Loading Windows 1. Run STARTNET.BAT to load the NetWare Lite software. 2. Type "NET LOGIN username" and press <Enter> to log in to the network. 3. Map drives and capture ports to set up your NetWare Lite environment. For more information on how to map drives and capture ports, see the manual. Load Windows If SYSTEM.INI was not changed as in the "Installing/Modifying NetWare Lite and Windows" section, NetWare Lite prevents Windows from loading, displays an error message, and returns you to the DOS prompt. If SYSTEM.INI was changed, NetWare Lite lets Windows load. When using Windows To access directories on a computer's local hard drive using a drive letter, use the DOS SUBST command instead of the NET MAP command. The SUBST command is more efficient than the NET MAP command for accessing directories on a local hard drive. For more information on the SUBST command, see your DOS documentation. Don't run the NET utility inside of a DOS box. When entering a DOS box in real or standard mode, immediately load TASKID by typing "TASKID" and pressing <Enter> at the DOS prompt. Just before exiting a DOS box in real or standard mode, unload TASKID by typing "TASKID U" and pressing <Enter> at the DOS prompt. If you are running executable (.EXE) command (.COM), or batch (.BAT) files that execute or spawn other executable, command, or batch files, and the files shut down, increase Windows' SYSTEM.INI file PSPIncrement value by increments of 5 until the files don't shut down. Before Printing in Windows Turn off the Fast Printing Direct to Port. From the Program Manager Main window, double click on the Control Panel icon, double click on the Printers icon, double click on the Connect button, and click on the Fast Printing to Direct Port box until it does not contain an X. Get application specific information for Windows from the NetWare Lite automated fax service. In the U.S. and Canada, call (800)638-9273 and press the asterisk (*) key at the beginning of the recorded message.